programming4us
           
 
 
Windows Server

Planning a Windows SBS 2011 Deployment

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
10/5/2011 11:38:40 AM
Planning is a crucial part of any network deployment process. The following sections guide you through the predeployment decisions you should make, including what hardware to purchase and what information you must have ready when you begin the installation.

1. Selecting Server Hardware

Obviously, you must have at least one server before you can install Windows SBS 2011. Table 1 lists the official system requirements for a server running Windows SBS 2011.

Table 1. System Requirements for a Windows SBS 2011 Server
PRIMARY SERVER
ProcessorQuad core x64 processor, 2 gigahertz (GHz) or faster 1 socket (4 sockets maximum)
Memory8 Gigabytes (GB) minimum,

10 GB recommended,

32 GB maximum
Available disk space120 GB minimum
Optical driveDVD-ROM drive
Network interfaceOne 10/100 Ethernet adapter
Graphic displaySuper VGA (1024 x 768) or higher resolution

The main requirement to consider is that the server running Windows SBS 2011 must have a 64-bit processor. In its default configuration, Windows SBS 2011 can run reasonably well on a computer with the minimum recommended hardware.

The actual hardware resources that a server running Windows SBS 2011 needs are based on a multiplicity of factors, including the following:

  • Number of users The more users who access the server, the more likely it is that you need additional hardware resources to support them.

  • Pattern of use Resource utilization increases when multiple users are working simultaneously. Therefore, an organization running a single shift of 30 clients will require more server resources than an organization running three shifts of 10 users each. Resource utilization also spikes if many users perform the same task at the same time, such as if 30 users log on to the domain at the same time each morning.

  • Request types Different types of client requests can require different server resources. For example, file services can benefit from increased storage subsystem performance, while Microsoft Exchange Server can benefit from both storage performance and memory upgrades.

  • Storage requirements The amount of storage that your applications and users require depends on their number and their activities. Users who work with video files require more storage than users working with still images, and both require much more storage than users who work primarily with text documents.

  • Additional applications If you plan to install additional applications on your server running Windows SBS, you must account for their hardware requirements in addition to those for the default server functions.

1.1. Processors

When selecting a processor for a server running Windows SBS 2011, you certainly do not want to skimp, but you should also be aware that the performance boost you realize from a faster processor might not be worth the expense. This is particularly true at the high end of the market; the latest and fastest processors are often a great deal more expensive than those a few steps down from the top of the line.

1.2. Memory

In a server configuration, it is more important to consider the amount of memory in the computer and the maximum amount it can hold instead of comparing memory types or speeds. Memory is usually the most inexpensive way to increase the performance of a server, or indeed any computer. For a server running Windows SBS 2011, 8 GB of memory is adequate, but 10 or 12 GB would be better. You should also make sure that your server supports at least twice as much memory as you have installed initially.


Tip:

When evaluating servers, you should consider the configuration of the memory modules as well. If the computer has 8 memory slots and you plan to install 8 GB initially, do not purchase a model that comes with eight 1 GB modules, as you will have to replace some of them when you upgrade.


1.3. Storage

Hard disk storage, like memory, is relatively inexpensive, and it is always a good idea to have more disk space than you think you need. However, for a server, you must consider not only the amount of storage space but also the configuration of the storage subsystem. Once you have decided how much storage space you need in your server, you must consider the nature of the data and its value to your organization.

Depending on the sensitivity of the data you plan to store on your server, and how critical the continued availability of that data is to your business, you might want to invest in a disk array that uses redundant array of independent disks (RAID) or some other high-availability technology. RAID is a system that uses two or more hard disk drives to store your data, along with duplicate or parity information that enables the server to survive a drive failure without data loss. Many servers are available with drive arrays that include RAID controllers, as well as other fault-tolerance features, such as hot-pluggable drives (drives that you can remove from the server and replace without having to shut the server down).

There are many different types of RAID, which are defined in numbered levels. Table 2 lists the RAID levels most commonly found in today’s servers and storage products. There are many other RAID implementations, some of which have rarely, if ever, appeared in the market, and others that are proprietary technologies of a specific manufacturer.

Table 2. RAID Levels Commonly Found in Server and Storage Products
RAID LEVELRAID FUNCTIONALITYMINIMUM NUMBER OF DISKS REQUIREDFAULT-TOLERANT?DESCRIPTION
RAID 0Stripe set without parity2NoThe system writes data one stripe at a time to each successive disk. No fault tolerance, but enhances performance.
RAID 1Mirror set without parity2YesAlso called disk mirroring, the system writes the same data to identical volumes on two different disks. Provides increased read performance, as well as fault tolerance.
RAID 5Stripe set with distributed parity3YesThe system stripes data and parity blocks across all the disks, without ever storing a block and its parity information on the same disk. Parity calculations add to system overhead, but provide more usable storage space than a mirror set.
RAID 6Stripe set with dual distributed parity4YesSame as RAID 5, except that the system stripes two copies of the parity information, along with the data, enabling the array to survive the failure of two drives.
RAID 0+1Mirrored stripe sets4YesThe system creates a stripe set and then mirrors it. Provides fault tolerance and improved performance. If a drive fails, its entire mirror set goes offline.
RAID 10 (or 1+0)Striped mirror sets4YesThe system stripes data across two or more mirror sets. Provides fault tolerance and improved performance. If a drive fails, all the remaining drives continue to function.
RAID 50 (or 5+0)Striped RAID 5 sets6YesThe system stripes data across two or more identical RAID 5 sets.

As long as you have the appropriate number of disk drives in the computer, Windows Server 2008 R2 can create volumes using RAID levels 0, 1, and 5. This is an inexpensive solution, but software-based RAID implementations can impose a penalty in system overhead. When you create a RAID 5 volume, for example, the same processor that performs all the other roles on your server must also calculate parity information for each block the system writes to the RAID array.


Note:

In Windows Server 2008 R2, RAID level 0 is referred to as a striped volume and RAID level 1 as a mirrored volume. Only RAID level-5 volumes use the RAID designation in Windows.


Hardware-based RAID takes the form of a dedicated host adapter, either integrated into the computer’s motherboard or implemented as an expansion card. The host adapter performs all the necessary functions, including parity calculations, so there is no additional burden on the system processor.

High-availability hardware products, such as RAID arrays, can add significantly to the cost of a server, and it is important to understand that this technology does not eliminate the need for regular system backups. Manufacturers design high-availability products for organizations that cannot tolerate server downtime. For example, if you run an order-entry application on your server, a hard disk failure can mean lost business and lost income, so the additional expense of a RAID array might be worthwhile. However, if a server outage due to a disk failure would be no more than a minor inconvenience to your organization, then standard hard disk drives might be a more reasonable and economical solution.

1.4. Other Server Components

In their basic components, servers are different from workstations only in matters of degree; they tend to have faster processors, more memory, and larger amounts of storage space, for example. They also have no more than rudimentary graphics and sound systems, as servers have no need for high performance in these areas.

However, as you can see in the case of the RAID storage solutions, server technologies are available that greatly enhance the performance and fault-tolerance capabilities of the computer. You can also purchase servers with redundant power supplies and fans, multiple processors, and many other elaborate and expensive components. In the case of a small-business server, however, most of these components are usually not necessary, and avoiding them can save you some money.

1.5. OEM or DVD?

You have two ways to purchase Windows SBS 2011: as a retail product, in which case you receive the product on DVDs, or as part of an original equipment manufacturer (OEM) package, in which case the product comes preinstalled on a computer. The OEM option is one solution to the problem of purchasing a suitable server to run Windows SBS 2011, but it does not save you a great deal of work. The Windows SBS installation process is quite simple, so if you can conceivably save money by purchasing the computer hardware and the Windows SBS 2011 product separately, you should do so.

2. Selecting Clients

The clients on a Windows SBS 2011 network must be running one of the following operating systems:

  • Windows 7 Professional

  • Windows 7 Enterprise

  • Windows 7 Ultimate

  • Windows Vista Business

  • Windows Vista Enterprise

  • Windows Vista Ultimate

  • Windows XP Professional with SP2 or later

  • Windows Mobile 5.0 or later

Table 3 lists the published system requirements for the Windows 7, Windows Vista, and Windows XP operating systems.

Table 3. System Requirements for Windows SBS 2011 Clients
 WINDOWS 7 PROFESSIONAL, ENTERPRISE, AND ULTIMATEWINDOWS VISTA BUSINESS, ENTERPRISE, AND ULTIMATEWINDOWS XP PROFESSIONAL SP2
Processorx86 or x64 processor, 1 GHz or fasterx86 or x64 processor, 1 GHz or fasterx86 processor, 300 megahertz (MHz) or faster
Memory1 GB minimum (32-bit) or 2 GB (64-bit)1 GB minimum128 megabytes (MB) recommended
Hard disk space40 GB, with 15 GB available40 GB, with 15 GB available1.5 GB available
Optical driveDVD-ROM driveDVD-ROM driveCD-ROM or DVD-ROM drive
Network interfaceEthernet or IEEE 802.11a/b/g/n wirelessEthernet or IEEE 802.11a/b/g/n wirelessEthernet or IEEE 802.11a/b/g/n wireless
Other -----------------
- Windows Small Business Server 2011 : A Networking Primer - Understanding Domains
- Windows Server 2008 : Using wbadmin (part 2) - Backing Up & Restoring Volumes with wbadmin
- Windows Server 2008 : Using wbadmin (part 1)
- Windows Home Server 2011 : Understanding Security Groups & Adding a New User
- Setting Up Your Windows Home Server 2011 Network : Handling Multiple Network Subnets & Making a Remote Desktop Connection to the Server
- Windows Small Business Server 2011 : A Networking Primer - Ethernet/IEEE 802.3 & TCP/IP Basics
- Windows Small Business Server 2011 : A Networking Primer - Networking Hardware
- Windows Server 2008 Server Core : Installing Applications with the MSIExec Utility
- Windows Server 2008 Server Core : Getting System Configuration Information with the SystemInfo Utility
- Setting Up Your Windows Home Server 2011 Network : Troubleshooting Network Problems (part 2)
- Setting Up Your Windows Home Server 2011 Network : Troubleshooting Network Problems (part 1)
- Windows Server 2008 : Working with Event Subscriptions - Managing Subscriptions with wecutil & Logging Events with eventcreate
- Windows Server 2003 : Managing Security Configuration with Security Templates (part 2)
- Windows Server 2003 : Managing Security Configuration with Security Templates (part 1)
- Setting Up Your Windows Home Server 2011 Network : Configuring Windows Home Server for Networking
- Introducing Windows Small Business Server 2011: Why Use Windows SBS 2011?
- Introducing Windows Small Business Server 2011: What is Included with Windows SBS 2011?
- Windows Server 2003 Security Configuration (part 2) - Creating Role-Specific Server Configurations
- Windows Server 2003 Security Configuration (part 1) - Windows Server 2003 Security Settings
- Windows Server 2008 Server Core : Accessing the WinPE Network Installer with the NetCfg Utility
 
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
- First look: Apple Watch

- 3 Tips for Maintaining Your Cell Phone Battery (part 1)

- 3 Tips for Maintaining Your Cell Phone Battery (part 2)
programming4us programming4us